I am creating an archive to deliver to a customer. Within the project there is some proprietary information. After the archive I am running a script to identify these objects an replace there text with a generic statement like "Proprietary Data Removed" The customer has agreed to this approach.
When I archive I only include the current baseline, but when I make the change a history record is created containing the very information I wish to remove. I can edit the attribute definitions on the custom attributes, but the option are all inactive for Object Text.
Is there a way to stop Object Text for generating a history record, or a way to delete the history record after it is created? Wicker - Thu Mar 13 14:02:37 EDT 2014 |
Re: Stop generating history for Object Text I after writing this post I began wondering, is the only reason I am seeing a long history changes is because there has not been a baseline struck in a while. If I make the change, then strike the baseline, then archive only the current baseline I seem to be able to mask the data I need to mask.
However, now the baseline number I send to the customer is different from the baseline number we work with internally. I need understand if this is a problem from either our firm or the customer.
It would be ideal if a solution can be found that would allow me to keep my baseline in sync. |
Re: Stop generating history for Object Text I'd be tempted to archive, restore to some playground; play with it cleaning it up; then archiving for sending to the customer. If your current baseline is "4.5c" then baseline the copy to "4.5c-Customer". If you find the location of the module in the database I would suppose you could realistically replace the "history.dtc" file in the "current Vers" folder with one from just-baselined module. I never play with the files but you can in your playground. If so, you won't need to baseline for sending to the customer. -Louie |